Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Docs refactor #35

Closed
wants to merge 36 commits into from
Closed

Docs refactor #35

wants to merge 36 commits into from

Conversation

smaldini
Copy link
Contributor

No description provided.

Jeff Brown and others added 30 commits October 11, 2010 12:28
…he link: namespace to generate links to named url mappings
…p for integration tests instead of creating another one.
… been using the storage of the TypeConvertingMap superclass.
…tart with a lower case letter followed by an upper case letter
…a nested fashion.

I suspect this was always the intended style of usage, but the implementation was bugged.
It needs to be because it's a singleton in the app.
…n the change is noticed.

Previously, observers where not being notified if a change was triggered manually using pluginManager.informOfClassChange().
…or POJO domain entities

- Corrected AbstractGrailsHibernateTests to set mainContext for grailsApplication
- Added unit test to verify a GrailsHibernateDomainClass' verifier has a messageSource
- Modified GrailsHibernateDomainClass to have a grailsApplication injected in its constructor, and use it to retrieve the messageSource
- Modified GrailsHibernateUtils to pass the grailsApplication instance to GrailsHibernateDomainClasses
…vent pages from being rendered in quirks mode
…lly broken in the previous commit but the test was using the default value so it appeared to work)
…idate. the list may contain the list of fields being validated.
…ist when no properties have been specified as arguments to validate()
…guide parts

now go in the same directory as 'api' and 'gapi', i.e. I've removed the 'manual'
sub-directory. Now when you open the documentation, the links between the guides
and the API docs work.
pledbrook and others added 6 commits November 3, 2010 11:50
…generate

pretty much the same Grails user guide as the old Generate.groovy in the
grails-doc project.

Summary of significant changes:

- DocEngine no longer provides default properties.
- DocPublisher provides default properties for the engine.
- If the engine properties are set on the DocPublisher, these override the
  default ones.
- Clients of DocPublisher can now register custom macros.
- PdfBuilder now assumes the current output structure for the documentation,
  i.e. no 'manual' directory.
…fted all

the HTML generation to the templates - DocPublisher no longer writes any HTML
itself.
…outs since

XHTML is pretty much required by Flying Saucer to generate the PDF.
@pledbrook
Copy link
Contributor

I'll deal with this. It needs to be pulled into docs-refactor branch.

@pledbrook
Copy link
Contributor

This is done, but I won't push to remote until we've worked out how to handle this with respect to the Grails 1.3.x releases.

@pledbrook
Copy link
Contributor

They won't go into 1.3.x since only blockers and regressions will be fixed in 1.3.x from here on.

jdaugherty pushed a commit to jdaugherty/grails-core that referenced this pull request Jan 9, 2025
grails#35)

Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
This pull request was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants