Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
blendb
blendb
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 23
    • Issues 23
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 1
    • Merge Requests 1
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Analytics
    • Analytics
    • CI / CD
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • C3SL
  • blendbblendb
  • Issues
  • #76

Closed
Open
Opened Apr 05, 2018 by Lucas Fernandes de Oliveira@lfoliveiraDeveloper
  • Report abuse
  • New issue
Report abuse New issue

Palavras compostas no arquivo de configuração YAML

O parsing das propriedades do arquivo de configuração é case sensitive isso faz com que chaves como enumType e dataType sejam diferentes de enumtype e datatype.

Seria prudente manter o padrão, ou realizar um preprocessamento para converter todas as propriedades para letras minúsculas ??

Uma diferentça dessa magnitude pode ser difícil de detectar em um processo de Debug. Como proceder ? Quão diffcíl seria converter apenas as chaves para letras minúsculas ? Seria prudente remover as palavars compostas e utilizar apenas palavars simples ?

To upload designs, you'll need to enable LFS and have admin enable hashed storage. More information
Assignee
Assign to
Revision
Milestone
Revision
Assign milestone
Time tracking
None
Due date
None
Reference: c3sl/blendb#76