I am trying go find an option that does this kind of highlighting that is quick/easy to use within a Jira ticket. The links below I have read through. I don't want to use a {code} bracket every time I want to highlight a keyword or attribute to pay attention to ie:
schema.tableName.myColumn = true.
You can easily do this within Microsoft Teams, Discord if you are having trouble understanding what I am looking for. Is there anything else that is in the works or currently out there for the Jira community to use? Something as easy as using tick marks?
Resources Viewed:
Using a {code} block
Highlighting words with <style>
Code Block Macro
Closest to this, out of the box is the {{monospaced}} formatting. Just enclose the text with double curly quotes {{,}}. No fancy syntax highlighting though. See Jira's Wiki Style Renderer guide.
If you like, you could also try this plugin Markin.
Related
I was wondering if autocomplete in Spyder editor(python) can show results on containing a part of a keyword rather than begins with part of a keyword, like now is the case. So if I type 'child'; the suggestion list also shows 'winfo_children'
(Spyder maintainer here) Unfortunately, that's not possible at the moment (December 2022), sorry.
Asana added rich text formatting in June 2014 (https://blog.asana.com/2014/06/rich-text/)
How do you get the formatting metadata from the Asana API?
For example, if I fill in a task description with:
some bold text. some italic text
a list
foo
bar
sublist
a
b
c
baz
The API returns the following for the note field, which excludes any formatting info:
"notes":"some bold text. some italic text\n\na list\n\nfoo\n\nbar\n\nsublist \na\nb\nc\nbaz"
We do not currently support rich text formatting via the API. However if you're feeling adventurous, we are currently working on this support, and you can try it out by using html_notes (for tasks) and html_text (for stories). You can request them using ?opt_fields=html_notes, for example.
Note however that this is still very experimental/early support. If the parser doesn't like the HTML you post, it just strips everything back to plaintext. So this is really only if you're feeling particularly adventurous - otherwise, I'd wait until we release full-fledged public support for it, with documentation and everything.
Is this still something "experimental"? I didn't want to post an answer but it won't let me comment the existing answer. So far I have found:
Acceptable
<b>
<ul>
<li>
Not acceptable:
<h4>
<p>
<div>
<section>
<br>
Any other suggestions for something to do a linebreak? Back in the day, I was using Wufoo to directly create tasks in Asana and it formatted it with a bold heading and then regular text for each entry data. I am trying to achieve this on my own without going that route because I am also updating a database when I receive the form submission. Any ideas on how to format (only the most basic of formatting)?
This question is fairly fundamental but I can't find a solution anywhere. There are many examples of highlighting text in javascript with or without jQuery, but I'm having trouble figuring it out in Dart.
The Selection and Range classes appear to support this but the documentation is kind of sparse.
Okay while trying to write the question thoroughly I figured it out. It's actually quite simple.
HTML: <p id='text'></p>
Dart:
var text = querySelector('#text');
Using Selection only:
window.getSelection().selectAllChildren(text);
Using Range and Selection:
var range = document.createRange();
range.selectNodeContents(text);
window.getSelection().addRange(range);
Both examples select all of the text inside the node. For more information on how to use Range, see this answer.
Site for writers and readers, both groups will be non-technical users (writers will be familiar with BBCode already, but I can choose other markup). Writers will write guides using markup tags to embodied info. Readers will be presented with parsed text. Tags will be expanded to some info.
Number of tags needed as well as info tied to particular tag will change. So they can not be hard-coded.
I'm looking for any interpreter that can use tags provided at run time, for my next Ruby on rails app. Anyone know such?
Edit: Yeah. I'm not looking for views markup, but for forms textarea markup to be used by website users (to format their guides, but I do need ONE markup for formatting, and embedding info).
Based on my current understanding of your needs, I recommend mustache. This is described as a "logic-less" template processor. It doesn't have programming logic, simply run-time replacements.
Here's one way to use it (from the github readme)
Given this template (winner.mustache):
Hello {{name}}
You have just won {{value}} bucks!
We can fill in the values at will:
view = Winner.new
view[:name] = 'George'
view[:value] = 100
view.render
Which returns:
Hello George
You have just won 100 bucks!
Tagsoup is interfering with input and formatting it incorrectly. For instance when we have the following markup
Text outside anchor
It is formatted as follows
Text outside anchor
This is a simple example but we have other issues as well. So we made tagsoup cleanup/formatting optional by adding an extra attribute to textarea control.
Here is the diff(https://github.com/binnyg/orbeon-forms/commit/044c29e32ce36e5b391abfc782ee44f0354bddd3).
Textarea would now look like this
<textarea skip-cleanmarkup="true" mediatype="text/html" />
Two questions
Is this the right approach?
If I provide a patch can it make it to orbeon codebase?
Thanks
BinnyG
Erik, Alex, et al
I think there are two questions here:
The first Concern is a question of Tag Soup and the clean up that happens OOTB: Empty tags are converted to singleton tags which when consumed/sent to the client browser as markup gets "fixed" by browsers like firefox but because of the loss of precision they do the wrong thing.
Turning off this clean up helps in this case but for this issue alone is not really the right answer because we it takes away a security feature and a well-formed markup feature... so there may need to be some adjustment to the handling of at least certain empty tags (other than turning them in to invalid singleton tags.)
All this brings us to the second concern which is do we always want those features in play? Our use-case says no. We want the user to be able to spit out whatever markup they want, invalid or not. We're not putting the form in an app that needs to protect the user from cross script coding, we're building a tool that lets users edit web pages -- hence we have turned off the clean-up.
But turning off cleanup wholesale? Well it's important that we can do it if that's what our usecase calls for but the implementation we have is all or nothing. It would be nice to be able to define strategies for cleanup. Make that function plug-able. For example:
* In the XML Config of the system define a "map" of config names to class names which implement the a given strategy. In the XForm Def the author would specify the name from the map.
If TagSoup transforms:
Text outside anchor
Into:
Text outside anchor
Wouldn't that be bug in TagSoup? If that was the case, then I'd say that it is better to fix this issue rather than disable TagSoup. But, it isn't a bug in TagSoup; here is what seems to be happening. Say the browsers sends the following to the client:
<a shape="rect"></a>After<br clear="none">
This goes through TagSoup, the result goes through the XSLT clean-up code, and the following is sent to the browser:
<a shape="rect"/>After<br clear="none"/>
The issue is on the browser, which transforms this into:
<a shape="rect">After</a><br clear="none"/>
The problem is that we serialize this as XML with Dom4jUtils.domToString(cleanedDocument), while it would be more prudent to serialize it as HTML. Here we could use the Saxon serializer. It is also used from HTMLSerializer. Maybe you can try changing this code to use it instead of using Dom4jUtils.domToString(). You'll let us know what you find when a get a chance to do that.
Binesh and I agree, if there is a bug it would be a good idea to address the issue closer to the root. But I think the specific issue he is only part of the matter.
We're thinking it would be best to have some kind of name-to-strategy mapping so that RTEs can call in the server-side processing that is right for them or the default if it's not specified.