Sebastian Hädrich

Results 101 issues of Sebastian Hädrich

* Change *string* to *struct* * So we can add a version history for engine

We have a listing for example in [lucee5.json](../blob/master/data/en/lucee5.json) which results in [Lucee 5 New Functions and Tags](https://cfdocs.org/lucee5). But what about deprecated or discouraged tags and functions?

There are some properties which are just a sub to specific function or tag just like a member function is for a specific data type. For example `columnList` or `recordcount`.

Could you please perform the following steps on the json of the example at [JSON Utilities](https://cfdocs.org/utilities/json/): - trim() the whole string - trim() the end of each line - replace...

Would it be nice to have both urls like `https://cfdocs.org/arraySet` (_works already_) and `https://cfdocs.org/array.set`?

@pfreitag Could you talk to [@Abram_Adams](https://twitter.com/Abram_Adams) from [trycf.com](https://trycf.com/about) that he installs some OSGi bundles to be used in some of our examples? Would be needed for #581.

You redirect * t to tags * f to functions * tag-summary to tags You **do not** redirect * a to all * g to guides * function-summary to functions...

Some functions have alternative syntax: - Shortcut like `#arrayNew()#` and `[]` - `queryExecute()` and `new Query()` - subset (function with specific parameter which has the same result as another function...

Should we add "functions and tags by engine" to navigation? Then we would have something like * [Lucee > Unsupported Tags & Functions](http://docs.lucee.org/reference/unsupported.html) * [Lucee > Additional Tags & Functions](http://docs.lucee.org/reference/additional.html)...

There are functions with arguments which can only be used when * Another argument is used as well * Another attribut has a specific value Should there be guides to...