Increase MaxLiteralCharacterLimit for loadTextContent (specifically for non-JSON content)
- Dominant language
- Bicep
- Stars
- 3.6k
- Forks
- 830
- Avg merge
- 1d 21m
- Merged PRs (30d)
- 79
Description
Increase MaxLiteralCharacterLimit for loadTextContent https://github.com/Azure/bicep/blob/main/src/Bicep.Core/LanguageConstants.cs#L32
Some of logic app JSON code as well as Azure Workbooks cannot be used with this function due to them being larger than 131072 characters. A lot of these resources would be created via azure portal and then used within arm templates/bicep for deployment. It would be great to have the ability to load it's content from within a separate file.
Contributor guide
Research direction
Start in src/Bicep.Core/LanguageConstants.cs at line 32 and trace loadTextContent. Determine how the 131072-character limit applies to non-JSON content and use the issue discussion to establish the intended new limit. Add coverage for oversized Logic App or Workbook-style content; done means larger valid content can be loaded as requested.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure, json
- Domain
- infrastructure
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100