add document build and deploy jobs

[SimeonEhrig]

solves #10

Copy of: QEDjl-project/QEDevents.jl#10

[SimeonEhrig]

@szabo137 Do you know, why the job fails?
https://github.com/QEDjl-project/QEDprocesses.jl/actions/runs/6467150725/job/17556628908?pr=19

[szabo137]

I will look into this. I assume some API change in Documenter.jl.

[SimeonEhrig]

I will look into this. I assume some API change in Documenter.jl.

Looks like this line of code causes the problem:

QEDprocesses.jl/src/interfaces/setup_interface.jl

Line 101 in 0074aa0

which should throw an exception, which is a subtype of [`AbstractInvalidInputError`](@ref). One may also use the concrete implementation [`InvalidInputError`](@ref) if the input is invalid instead of writing a custom exception type.

[SimeonEhrig]

I will look into this. I assume some API change in Documenter.jl.

Looks like this line of code causes the problem:

QEDprocesses.jl/src/interfaces/setup_interface.jl

Line 101 in 0074aa0

which should throw an exception, which is a subtype of [`AbstractInvalidInputError`](@ref). One may also use the concrete implementation [`InvalidInputError`](@ref) if the input is invalid instead of writing a custom exception type.

@szabo137 Looks like, the documentation references an error type, which does not exist. I didn't found anything in the QED projects and also not in the official documentation.

[AntonReinhard]

It should be AbstractInvalidInputException, that's what is defined. But it is a little weird that one is SomethingException and the other is SomethingError, so we should probably use one of the two consistently everywhere. I think I would prefer Exception, Error is less specific.

So I'd suggest renaming the InvalidInputError to InvalidInputException, too.

[SimeonEhrig]

It should be AbstractInvalidInputException, that's what is defined. But it is a little weird that one is SomethingException and the other is SomethingError, so we should probably use one of the two consistently everywhere. I think I would prefer Exception, Error is less specific.

So I'd suggest renaming the InvalidInputError to InvalidInputException, too.

Yes, you are right. We are a little bit inconsistent 😅

QEDprocesses.jl/src/interfaces/setup_interface.jl

Lines 79 to 83 in 0074aa0

	Exception which is thrown if a given input is invalid, e.g. passed to [`_assert_valid_input`](@ref).
	"""
	struct InvalidInputError <: AbstractInvalidInputException
	msg::String
	end

Nevertheless, I would fix the error in the documentation now and we do the possible renaming in an extra PR.

[szabo137]

Nothing to bother, merging!