* Initial commit
* WIP
* Fix lint
* Fix tests
* Add test for workspace migration
* Rename title to use fileName instead of workspace name for designer
* Linting
* Add breaking test
* Remove preferential ordering of tags over variables in nunjucks
* Remove preferential ordering of tags over variables in nunjucks
* simplify nunjucks sort
* Add breaking test for incorrect order
* Update json-order and consume
* Refine test with dataPropertyOrder
* Tests
* add note
* Add to test
* Missed the await
* Update nunjucks-tags.js
(Fixes bug #1288) Extract parent from nunjucks tag when it is a nested property nested. The parent is then used to fetch the keyContext
* Revert "Update nunjucks-tags.js"
This reverts commit 4d4da99de3.
* Update render.js
Added function that recursively gets the keys. So they will show the correct parent location in the nunjuck tooltip.
* Rework after review from gschier
A few little changes after review of the initial change.
* Added keySource for Arrays
Added loop to store Key and Source when item is an Array.
* Add pinning behavior
* add fa-thumb-tack
* Updated package-lock files
* Allow only top level request and request group to be pinned
* Prevent dnd for pinned request
* Efficiency change
* Reverted changes
* Revert changes to selectors.js
* Fixed pin and add thumbtack
* Changes
* Pin styling
* Fix overflow bug
* styling complete
* Remove additional style
* Updated package-lock.json
* Mergie
* Boolean to boolean
* allow nested requests to be pinned
* Remove unused arg
* Remove folder pinning functionality
* Remove comment
* Revert change to open tag on group
* Render separator with dsiplay: none so that sync menu is in correct place
* Don't reset parent id on request pin
* Remove extra checks
* Move pin filter to selectors to prevent duplicate childTree traversal
* Decouple pinned items from search results
* Hide pin on hover
* Pin keyboard shortcut via shift+ctrl+p
* Typo fix
* Update mac hotkey + activeRequest nullcheck
* Disable drag and drop only for items in the pinned list
* Filter to Find
The https://developer.mozilla.org/en-US/docs/Web/HTTP/Status page do say that the 405 should not be returned for GET and HEAD. But if you click on that 405 link it will open https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/405 , and there there's nothing about mandatory methods.
On that page you will get the RFC link https://tools.ietf.org/html/rfc7231#section-6.5.5 , and again, there's nothing about mandatory methods.
The restful documentation also doesn't talk about mandatory methods for 405: https://restfulapi.net/http-status-codes/
Spring Framework (a well know framework for Java) has some configuration for the Spring Data Rest project that will result in GET requests returning 405.
Since the RFC should be the winner here, and the divergence between the mozilla's pages, I'm proposing this fix to remove the misleading description.
